Problem Note 62063: You might encounter “ERROR: Unable to transcode data to/from UCS-2 encoding” when running a UTF-8 SAS® session and using SAS/ACCESS® Interface to ODBC
When you run a UTF-8 encoded SAS session and SAS/ACCESS Interface to ODBC, you might encounter the following error:
ERROR: Unable to transcode data to/from UCS-2 encoding.
You encounter this issue when you use a LIBNAME statement to write character-type data to a target ODBC database.
For example, you would encounter this issue if you ran the following code:
libname db odbc dsn=data-source-name;
proc sql;
insert into db.my_nvar2(NULLCHAR=NO NULLCHARVAL=' ') select * from work.employee ;
quit;
SAS/ACCESS Interface to ODBC contains a bug that does not allocate enough space for the value that replaces the null character. In the example code above, the value that replaces the null character is a blank set in the NULLCHARVAL option.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to ODBC | Windows 7 Ultimate x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Ultimate 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Professional x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Professional 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Home Premium x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Home Premium 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Enterprise 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Std | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Std | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Datacenter | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2008 for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2008 R2 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2008 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 10 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Pro x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Pro 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft® Windows® for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
64-bit Enabled AIX | 9.4 TS1M4 | 9.4 TS1M5 |
64-bit Enabled Solaris | 9.4 TS1M4 | 9.4 TS1M5 |
HP-UX IPF | 9.4 TS1M4 | 9.4 TS1M5 |
Linux for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Solaris for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
This error occurs when you use a LIBNAME statement to write character-type data to a target ODBC database.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2018-05-09 15:38:34 |
Date Created: | 2018-03-28 14:16:13 |